home *** CD-ROM | disk | FTP | other *** search
/ Internet Info 1997 December / Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso / ietf / urn / urn-archives / urn-ietf.archive.9611 / 000077_owner-urn-ietf _Wed Nov 6 20:13:32 1996.msg < prev    next >
Internet Message Format  |  1997-02-19  |  2KB
  1. Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id UAA20869 for urn-ietf-out; Wed, 6 Nov 1996 20:13:32 -0500
  2. Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id UAA20864 for <urn-ietf@services.bunyip.com>; Wed, 6 Nov 1996 20:13:30 -0500
  3. Received: from IG.CS.UTK.EDU by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
  4.         id AA15932  (mail destined for urn-ietf@services.bunyip.com); Wed, 6 Nov 96 20:13:25 -0500
  5. Received: from localhost by ig.cs.utk.edu with SMTP (cf v2.11c-UTK)
  6.           id UAA15866; Wed, 6 Nov 1996 20:12:46 -0500 (EST)
  7. Message-Id: <199611070112.UAA15866@ig.cs.utk.edu>
  8. X-Uri: http://www.cs.utk.edu/~moore/
  9. From: Keith Moore <moore@cs.utk.edu>
  10. To: "Karen R. Sollins" <sollins@LCS.MIT.EDU>
  11. Cc: moore@cs.utk.edu, urn-ietf@bunyip.com
  12. Subject: Re: [URN] I18N does not belong in URNs 
  13. In-Reply-To: Your message of "Wed, 06 Nov 1996 20:06:02 EST."
  14.              <199611070106.UAA09788@lysithea.lcs.mit.edu> 
  15. Date: Wed, 06 Nov 1996 20:12:46 -0500
  16. Sender: owner-urn-ietf@services.bunyip.com
  17. Precedence: bulk
  18. Reply-To: Keith Moore <moore@cs.utk.edu>
  19. Errors-To: owner-urn-ietf@bunyip.com
  20.  
  21. > I would like to be more specific about Keith Moore's statement:
  22. > 
  23. >    URNs should be precise enough that a human isn't required to
  24. >    disambiguate the result.
  25. > 
  26. > In particular, in light of the following requirement from RFC 1737
  27. > 
  28. >    o Global uniqueness: The same URN will never be assigned to two
  29. >      different resources.
  30. > 
  31. > the URN will refer to exactly one resource from the perspective of
  32. >                                            ^^^^^^^^^^^^^^^^^^^^^^^
  33. > that naming authority assigning the name.  
  34.  
  35. Yes, this is exactly correct.
  36.  
  37. But what this means is that if you ask the naming authority to do
  38. resolution on a URN, you won't get back references to multiple resources.
  39.  
  40. Contrast this with a search for matches to a user-friendly string,
  41. which always has the potential for multiple hits.
  42.  
  43. Keith